home *** CD-ROM | disk | FTP | other *** search
Text File | 1990-05-04 | 1.2 KB | 29 lines | [TEXT/GEOL] |
- Item 6193815 30-April-90 06:51PDT
-
- From: A14 Carnegie Mellon, Rob Chandok,PRA
-
- To: MACAPP.TECH$ MacApp Technical
-
- Sub: DoSetCursor again
-
- Dave Wilson points out that my method of getting the cursor to change quickly
- steals cycles from other tasks under Multifinder. And I agree.
-
- But TANSTAAFL, eh? Something has to compute what to set the cursor to, and if
- you application is doing it, it is taking up cycles. You either get the
- response time, or the sleep time, not both.
-
- Some computer systems allow you to tell the OS or some hardware what to set the
- cursor to when you are over a particular region of the screen. Thus, your task
- dosn't change the cursor, but somebody does it for you (and they spend cycles
- to). This doesn't account well for option keys and the like in an environment
- like the Mac where option key transitions don't cause events.
-
- I have to agree with Dave that setting fIdleFreq is kind of awkward. Maybe
- there should be an application or view method called "SetLiveCursor" that could
- inform the App when it had to be more careful about calling DoSetCursor more
- often.
-
- Rob
-
-